Yup, I’ve just reinstalled previous emulator. Now it doesn’t work. The emu itself is up, but games won’t boot.

I also noticed that I’ve been using uae4all this whole time. I was convinced it had been uae4arm. Anyway, all worked in most cases, arm and berry don’t. But now all doesn’t as well.

Please excuse my mistakes. I’m aware they’re silly, but I’m a bit lost.

I think it is fixed. I reboot multiple times and only once it flicked black for about 1/2 a second.

I moved my splash screen to /opt/retropie/supplementary/splashscreen/

then I

edited asplashscreen.sh and removed the -b from around line 37 near OMX (that removed a black background that used to be needed to hide post text.

I had to use the command sudo chown on the directory to get write access

@vodkanakas TeamViewer needs an X.org server running to be working, ES - the version for the Pi - does not run in a X.org session, so you cannot see ES via TeamViewer.

Never mind... it appears updating works.

@darksavior Thanks, I think this might be it, because it freezes right at the playstation logo, I tried finding info in english on it but can't, any suggestions on how I could try find any info on this?

However , thinking about it a bit more, the higher the voltage and lower the amps, the less the resistance of the cable/fuse causes issues with heating etc, and lower voltage and amps cause higher heating due to resistance,

since polyfuses (according to wikipedia) "trip" from the heat build up during use. The lower voltage and higher amperage would heat it more, thus making it "trip"

@scopaust said in 0.78 Romset Retropie Black Screen:

One more question, how do I know what bios is required by a MAME2003 game

You could use a ROM manager like Romcenter to see the ROM details or look in the compatibility list (https://docs.google.com/spreadsheets/d/1LP1MELCvcxu7TfiowF_0ZuvRVEMqlfQyTVetnOJvuJc/edit?usp=sharing).

[SOLVED]

I noticed that in the main retroarch.cfg file there was a setting as follows:

# Toggles fullscreen. # input_toggle_fullscreen = f

I wasn't aware that a commented line means that the "default" is still enabled. (ie: "f" is still enabled to toggle fullscreen).

I've now changed this to the following (ie: replaced "f" with "nul") and the "problem" is now resolved:

# Toggles fullscreen. input_toggle_fullscreen = nul

@mediamogul Thanks for taking your time to reply. Alright i thought it was something i did. Will do exactly what you said Mediamogul from now on when using that emulator. Thanks again.

I ended up finding a solution. A fresh image seemed to have solved all the issues. Not entirely sure why, but I think it may have something to do with the way my GPIO pins were set for the Borkin button.

Hate having to start over, but it's nice to be up and operating again!

@thedatacereal

On some n64 games the Emulator menu pops up... but I've ran into some... that do not give prompt, just a black screen until the rom loads ...I swear I just accessed that menu on Mario Kart the other day

It sounds like another emulator was launched prior to you using the N64 emulator and left the framebuffer in an unusable state. Two emulators that are currently known to do this are the standalone version of Stella (Atari2600) and DraStic (Nintendo DS). If such an issue happens, there's really nothing to do but restart your system, as restarting Emulation Station isn't enough.

@rion Perfect! Now it works. Thank you.
I recently faced crashes on Driver by select "Try Mission Again" after I fail a mission.
Any idea how to fix that?

I downloaded it.

@tostati you can still set Kodi to 1080p btw whilst using 720p for everything else. Kodi on RetroPie restores the previous video mode on exit. I use 720p but boot to Kodi which switches to 1080p. Then I exit to es, and have 720p again.

@shayne66 OK so I have no experience with that chipset. However, a quick Google around revealed that Foxconn refuses to play nicely with Linux back when this board was in use. Foxconn is a large OEM motherboard manufacturer, but according to a thread on the Ubuntu Forums, they refuse to support Linux. There is a bug in one of their DSDT tables for their BIOS that's causing installation and lock up issues. Now this was years ago but since you have an old board, if it's BIOS is original then maybe you are experiencing the hell that many did years ago. If you have played a ROM and now you cannot, then it probably points to an installation problem. I have never heard of a rom working and then not working unless configs and/or the emulator was changed via the runcommand.

@mr-monkeyface Update RetroPie and packages from the RetroPie menu: https://retropie.org.uk/docs/Updating-RetroPie/